The cw-json repository now has version 0.4.0 of kmp-jsonpointer and kmp-jsonpointer-kxs.
In addition to the official JSON Pointer means of navigating JSON, this release adds unofficial-but-popular dot notation. It is the sort of syntax you see in template languages like Mustache, Handlebars, and Liquid. foo.bar.goo in dot notation is equivalent to /foo/bar/goo in official JSON Pointer syntax.
JsonPointer.from() now accepts all three core syntaxes:
There are dedicated functions like JsonPointer.fromDotNotation() for cases where you know the exact syntax that you want to support.
There is also a toDotNotation() function on JsonPointer instances that will give you the dot notation form of the pointer.
The Dokka documentation has been updated for 0.4.0.
—Jun 08, 2026
No new-to-us artifact groups or artifacts this week, but we did get new versions of nearly 400 existing artifacts – check them out here!
—Jun 03, 2026
In tandem with Google I|O 2026, we got nearly 1000 new artifact versions!
However, no new artifacts appeared, let alone artifact groups.
😑
—May 20, 2026
Media3 gave us patch releases for 1.9.x and 1.10.x:
androidx.gradle:gradle-version-catalog:2026.05.00androidx.gradle:gradle-version-catalog-alpha:2026.05.00androidx.gradle:gradle-version-catalog-beta:2026.05.00androidx.media3:media3-cast:1.10.1androidx.media3:media3-cast:1.9.4androidx.media3:media3-common:1.10.1androidx.media3:media3-common:1.9.4androidx.media3:media3-common-ktx:1.10.1androidx.media3:media3-common-ktx:1.9.4androidx.media3:media3-container:1.10.1androidx.media3:media3-container:1.9.4androidx.media3:media3-database:1.10.1androidx.media3:media3-database:1.9.4androidx.media3:media3-datasource:1.10.1androidx.media3:media3-datasource:1.9.4androidx.media3:media3-datasource-cronet:1.10.1androidx.media3:media3-datasource-cronet:1.9.4androidx.media3:media3-datasource-okhttp:1.10.1androidx.media3:media3-datasource-okhttp:1.9.4androidx.media3:media3-datasource-rtmp:1.10.1androidx.media3:media3-datasource-rtmp:1.9.4androidx.media3:media3-decoder:1.10.1androidx.media3:media3-decoder:1.9.4androidx.media3:media3-effect:1.10.1androidx.media3:media3-effect:1.9.4androidx.media3:media3-effect-lottie:1.10.1androidx.media3:media3-exoplayer:1.10.1androidx.media3:media3-exoplayer:1.9.4androidx.media3:media3-exoplayer-dash:1.10.1androidx.media3:media3-exoplayer-dash:1.9.4androidx.media3:media3-exoplayer-hls:1.10.1androidx.media3:media3-exoplayer-hls:1.9.4androidx.media3:media3-exoplayer-ima:1.10.1androidx.media3:media3-exoplayer-ima:1.9.4androidx.media3:media3-exoplayer-midi:1.10.1androidx.media3:media3-exoplayer-midi:1.9.4androidx.media3:media3-exoplayer-rtsp:1.10.1androidx.media3:media3-exoplayer-rtsp:1.9.4androidx.media3:media3-exoplayer-smoothstreaming:1.10.1androidx.media3:media3-exoplayer-smoothstreaming:1.9.4androidx.media3:media3-exoplayer-workmanager:1.10.1androidx.media3:media3-exoplayer-workmanager:1.9.4androidx.media3:media3-extractor:1.10.1androidx.media3:media3-extractor:1.9.4androidx.media3:media3-inspector:1.10.1androidx.media3:media3-inspector:1.9.4androidx.media3:media3-inspector-frame:1.10.1androidx.media3:media3-muxer:1.10.1androidx.media3:media3-muxer:1.9.4androidx.media3:media3-session:1.10.1androidx.media3:media3-session:1.9.4androidx.media3:media3-test-utils:1.10.1androidx.media3:media3-test-utils:1.9.4androidx.media3:media3-test-utils-robolectric:1.10.1androidx.media3:media3-test-utils-robolectric:1.9.4androidx.media3:media3-transformer:1.10.1androidx.media3:media3-transformer:1.9.4androidx.media3:media3-ui:1.10.1androidx.media3:media3-ui:1.9.4androidx.media3:media3-ui-compose:1.10.1androidx.media3:media3-ui-compose:1.9.4androidx.media3:media3-ui-compose-material3:1.10.1androidx.media3:media3-ui-compose-material3:1.9.4androidx.media3:media3-ui-leanback:1.10.1androidx.media3:media3-ui-leanback:1.9.4
—May 13, 2026
As I have gotten back into publishing open source code, the age-old question arose: where do I host the source code?
My original solution was GitHub. I moved away from it several years ago, because I felt that it was far too powerful of an entity, especially as a subsidiary of Microsoft. They have had outage issues and claiming CoPilot wrote all the things. On top of that, I keep reporting malware and they keep not doing anything about it. So, I am not about to hand over more stuff to them if I can avoid it.
For a while, I was using GitLab. They weren’t bad, but they still worried me with some of their decisions.
Now? I am using Codeberg. I like their non-profit status. Many people will appreciate that they are based in Europe, or that their primary social media presence is on Mastodon. I do not have very sophisticated needs from a source repository, and they cover those needs nicely. I do worry a bit about what happens if they get slammed with a DDoS or other attacks, but otherwise, I feel better about using them than I do using their huge competitors.
—May 10, 2026
